Preserve Retain Route Target All on Boarder Leaf Devices

XCO preserves the retain route-target all configuration on boarder leaf devices in any config sync operations (for example, any sync refresh from XCO to IP fabric).

In XCO 3.5.0, the retain route-target all configuration is applied under "l2evpn address-family" on the spine and super-spine devices, but not on the leaf and border-leaf devices. If you manually configure retain route-target all as out-of-band on the border-leaf or leaf devices, XCO detect this as a drift and reconcile..

Starting from XCO 3.6.0, for Data Center Interconnect (DCI) scenarios, ensure that the retain route-target all configuration is present on the border-leaf devices. Therefore, XCO will no longer manage the retain route-target all configuration, specifically, on the border-leaf devices. This means that XCO will neither configure nor detect drift and reconcile for any retain route-target all configuration on the border-leaf devices, except for non-Clos multi rack fabric.

The following table describes the retain route-target all configuration for a non-Clos and Clos fabric:
Fabric Type Device Type Description
Non-Clos Singel Rack Border Leaf XCO does not push 'retain route-target all' on leaf or border-leaf devices, so it disowns the 'retain route-target all' configuration for these devices.
Multi Rack Border Leaf or Leaf XCO preservers the 'retain route-target all' configuration, configures it as part of the fabric configuration, and detects and reconciles any drift during DRC.
Clos (3-Stage or 5-Stage) Border Leaf XCO disowns the 'retain route-target all' configuration, neither configuring it nor identifying and reconciling drift as part of DRC.

Example Configuration for Non-Clos Single Rack Fabric

The following is an example configuration for non-Clos single rack fabric:

efa fabric show --name common-fabric
Fabric Name: common-fabric, Fabric Description: , Fabric Type: non-clos, Fabric Status: configure-success, Fabric Health: Green 
+--------------+-------+-----------+------------+------------+--------------+-------------+-------------------+-----------------+---------+-------+
|  IP ADDRESS  | RACK  | HOST NAME |    ASN     |    ROLE    | DEVICE STATE |  APP STATE  | CONFIG GEN REASON | PENDING CONFIGS | VTLB ID | LB ID |
+--------------+-------+-----------+------------+------------+--------------+-------------+-------------------+-----------------+---------+-------+
| 10.64.208.22 | r1    | SW-22     | 4200065535 | BorderLeaf | provisioned  | cfg in-sync | NA                | NA              | 2       | 1     |
| 10.64.208.23 | r1    | SW-23     | 4200065535 | BorderLeaf | provisioned  | cfg in-sync | NA                | NA              | 2       | 1     |
+--------------+-------+-----------+------------+------------+--------------+-------------+-------------------+-----------------+---------+-------+

Example

The following examples show the retain route-target all configuration behavior in XCO 3.5.0 and 3.6.0 in a non-Clos single rack fabric:

Example Configuration for Non-Clos Multi Rack Fabric

The following is an example configuration for non-Clos multi rack fabric:

efa fabric show –name fs
Fabric Name: fs, Fabric Description: , Fabric Type: non-clos, Fabric Status: configure-success, Fabric Health: Green
+--------------+------+-----------+------------+------------+--------------+-------------+-------------------+-----------------+---------+-------+
|  IP ADDRESS  | RACK | HOST NAME |    ASN     |    ROLE    | DEVICE STATE |  APP STATE  | CONFIG GEN REASON | PENDING CONFIGS | VTLB ID | LB ID |
+--------------+------+-----------+------------+------------+--------------+-------------+-------------------+-----------------+---------+-------+
| 10.64.208.28 | r1   | S28       | 4200000000 | leaf       | provisioned  | cfg in-sync | NA                | NA              | 2       | 1     |
| 10.64.208.29 | r1   | S29       | 4200000000 | leaf       | provisioned  | cfg in-sync | NA                | NA              | 2       | 1     |
| 10.64.208.23 | r2   | L23       | 4200065535 | borderleaf | provisioned  | cfg in-sync | NA                | NA              | 2       | 1     |
| 10.64.208.22 | r2   | L22       | 4200065535 | borderleaf | provisioned  | cfg in-sync | NA                | NA              | 2       | 1     |
+--------------+------+-----------+------------+------------+--------------+-------------+-------------------+-----------------+---------+-------+

Example

The following examples show the retain route-target all configuration behavior in XCO 3.5.0 and 3.6.0 in a non-Clos multi rack fabric:

Example Configuration for Clos Fabric

The following is an example configuration for a Clos fabric:

efa fabric show --name stage5
Fabric Name: stage5, Fabric Description: , Fabric Stage: 5, Fabric Type: clos, Fabric Status: configure-success, Fabric Health: Green
+--------------+-----------+-----------+-------+------------+--------------+-------------+-------------------+-----------------+---------+-------+
|  IP ADDRESS  |    POD    | HOST NAME |  ASN  |    ROLE    | DEVICE STATE |  APP STATE  | CONFIG GEN REASON | PENDING CONFIGS | VTLB ID | LB ID |
+--------------+-----------+-----------+-------+------------+--------------+-------------+-------------------+-----------------+---------+-------+
| 10.64.208.29 | podstage5 | S29       | 64769 | superspine | provisioned  | cfg in-sync | NA                | NA              | NA      | 1     |
| 10.64.208.28 | pod3      | S28       | 64512 | spine      | provisioned  | cfg in-sync | NA                | NA              | NA      | 1     |
| 10.64.208.22 | pod3      | L22       | 65000 | leaf       | provisioned  | cfg in-sync | NA                | NA              | 2       | 1     |
| 10.64.208.23 | pod3      | L23       | 66000 | borderleaf | provisioned  | cfg in-sync | NA                | NA              | 2       | 1     |
+--------------+-----------+-----------+-------+------------+--------------+-------------+-------------------+-----------------+---------+-------+

Example

The following examples show the retain route-target all configuration behavior in XCO 3.5.0 and 3.6.0 in a Clos fabric: